This chapter introduces the Advance Users, or Administrators, to create Classes, Lifecycles, Workflows: § Manage Class Interface § Manage Lifecycle Interface § Manage Workflow Interface |
While a user is working with objects in 4G:PLM, he/she will be working with the object’s classes and subclasses. They will have to define it’s lifecycles and also will be defining the production workflow.
Companies often group like objects into different classes. These classes share common attributes, can be searched as a group, and access to them can be managed as a group.
For example, a company that manages its parts in a database will have a “parts” class. All parts may have attributes such as “part number” and “description”. This will not be sufficient to store information on parts that engineers must search on. They require different information for a screw than for a resistor. Therefore, a company might introduce two part subclasses, one for screws and one for resistors. The “screw” subclass might get the attributes “length” and “type”, whereas the “resistor” subclass might have the attributes “resistance” and “power”.
Figure 4.1: Classes & Subclasses
It is also possible to create new subclasses for parts, documents and engineering change orders.
In other words, in 4G:PLM, an “Item” is a “Class”, an “Assembly” is a “Subclass”.
The Manage Classes interface allows users to manage classes. Users can create a new class, delete classes and update information.
To create a new “Class”, and/or a “Subclass”, in 4G:PLM:
I. Go to “Admin” menu
II. Select “Classes”
III. Select “New Class” button
IV. Give the Class a name and a description
V. Click “OK” button to confirm the creation of a new Class
VI. To add “Subclasses” to that class click “New Subclass”
VII. Select a “Class”(from the drop down menu), give a name for the “Subclass”, give a description
VIII. Click “OK” button to save the Subclass
IX. In the “Modify Class” window, give the required details for the Subclass:
· Type Description · Prefix |
· Postfix · Maximum Number |
X.
Click the button to save
the Subclass